OpenZeppelin issue:
Throughout the codebase, there are several validation issues that can be corrected:

The NatSpec comment for ACTION_THRESHOLD describes it as the "Minimum liquidity required to continue," which implies the value 1e12 is an inclusive lower bound for an action to proceed. However, within the _burnOethOnTheContract function, this threshold must be exceeded, making the threshold an exclusive boundary and contradicting the NatSpec comment. Consider updating the NatSpec comment to clarify that the amount must be "greater than" the threshold to align with the code's logic.
The validation checks in _getAddLiquidityParams use a strict greater-than (>) comparison to ensure the calculated required token amounts are less than the maximum available balances. This logic is overly restrictive and will incorrectly cause the transaction to revert in valid scenarios where the required amount is exactly equal to the contract's available balance. To fix this and allow the strategy to correctly deploy its full token balance when necessary, consider changing the comparison operators from > to >=.
Consider fixing these issues to ensure the validations are correctly aligned with intended behavior